Using Primary, Secondary, and Tertiary RTF Sequences

When you set up a routing sequence for a requester branch, you are effectively defining the branches that the requester branch can share filling hold requests with, whether items are taken off the shelf as part of RTF processing or trapped at circulation. When you are considering what branches to include in your RTF sequences, also consider the following:

  • Aligned Policies: Include branches that have similar holds policies to the requesting library so that the item can be loaned without confusion.

  • Agreements: Include branches that the requesting library has already contacted to secure an RTF agreement.

The recommended use of the three sequences is dependent on your goal.

  1. Fill Request as Fast as Possible — Define only Primary RTF Sequence

    In a system where libraries are geographically close and have similar lending policies, a branch might define only a primary group of RTF branches. The library might place itself with a few geographically close or politically allied branches in the primary group. This setup allows a request to pass from one branch to the other in a preferred order. If you leave a branch out of a routing cycle, that prevents your items from filling requests at that branch.

  2. Fill Holds while Balancing Cost Savings — Define two or three RTF Sequences

    RTF Sequences allow a library to establish levels of priority in filling hold requests. If the concern is to balance cost, policies, and agreements, the library might create the primary group and secondary or tertiary groups. Then the library has a choice to prioritize branches into three groups.

    To save cost, include in the secondary group, branches that are local to the requesting library so that the item can be shipped at a low cost. An example could be the branches that are on a certain route that the mobile library or courier service already travels. The tertiary group might include branches that are regional to the requesting library. An example might be all branches left in the region of the requesting library that are not already in a sequence.